Hi everybody. We recently have updated SCOM 2007 R2 with RU5. We have modified these 2 files: Microsoft.MOM.ConfigServiceHost.exe.config and Microsoft.MOM.Sdk.ServiceHost.exe.config in order to avoid "system Center configuration service" start problems. After the update , this service starts successfully, but now, the System Center Management Configuration service stop regularly after minutes or hours with events 7000 in system log: "The System Center Management Configuration service terminated unexpectedly" I have observed also that the transaction log for operational database is full with evetns 9002 in application log since few days.. "The transaction log for database 'OperationsManager' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases" My question: is the "transaction log for operational database" size problem related to the "System Center Management Configuration service" problem ? If no, any clue to solve the problem will be appreciated.. Thanks in adavnce. Regards..

well it's definitely a problem for your management group. i'd say fix the db issue first (seems like a fixed sized if possible you might want to set autogrow for now).Rob Korving http://jama00.wordpress.com/

Hi If the transaction log is full, can you check the recovery model that you are using on the database. If you have Full Recovery then you need to make sure that you are taking log backups otherwise the transaction log will continue to grow ad infinitum (or at least until the disk is full - whichever comes first!). If you have Simple recovery model then to a large extent, SQL takes care of the transaction log itself though as Rob says, you might want to allow it to autogrow. http://www.databasejournal.com/features/mssql/article.php/3782401/SQL-Server-2008-Recovery-Models-and-Backups.htm If the transaction log is full then that could cause the problems you are seeing. A full transaction log means that no more changes can be written to the database (as the transaction log records changes) which might well cause service crashes. Cheers GrahamRegards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Hi, In addition, regarding transaction logs, please also see: What SQL maintenance should I perform on my OpsMgr databases? http://blogs.technet.com/b/kevinholman/archive/2008/04/12/what-sql-maintenance-should-i-perform-on-my-opsmgr-databases.aspx SQL Server for Operations Manager 2007 http://technet.microsoft.com/en-us/library/bb432135.aspx Hope this helps. Thanks. Nicholas Li TechNet Community Support

Hi everybody. Thanks for your responses. We effectively corrected the transaction log problem. The database was in "Full recovery", and used autogrow with a maximum size for the size of the log. The log was not backed up since few days. The backup problem was solved, and now , it is corrected. We don't have anymore errors related to that. Unfortunately, we have always the problem for the service "System Center Management Configuration" which continue to stops.. "The System Center Management Configuration service terminated unexpectedly" (Event 7000) Any other clues will be appreciated. Thanks Again. Regards.

Hi, Please try the following method: Note: Please perform a full backup before doing this. 1. Stop all of the SCOM services: System Center Management service System Center Management Configuration service System Center Data Access service 2. Go to Registry Editor, remove sub keys for OpsMgr Config Service from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application 3. Remove OpsMgr Config Service from Sources located at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application 4. Add OpsMgr Config Service to Sources at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Operations Manager 5. Restart the server. Hope this helps. Thanks. Nicholas Li TechNet Community Support

Hi Nicola. I checked the registry on the server, and effectively, we have found an entry "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\OpsMgr Config Service" with 1 subkey EventMessagefile. EventMessageFile"=hex(2):43,00,3a,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,\ 00,73,00,5c,00,4d,00,69,00,63,00,72,00,6f,00,73,00,6f,00,66,00,74,00,2e,00,\ 4e,00,45,00,54,00,5c,00,46,00,72,00,61,00,6d,00,65,00,77,00,6f,00,72,00,6b,\ 00,36,00,34,00,5c,00,76,00,32,00,2e,00,30,00,2e,00,35,00,30,00,37,00,32,00,\ 37,00,5c,00,45,00,76,00,65,00,6e,00,74,00,4c,00,6f,00,67,00,4d,00,65,00,73,\ 00,73,00,61,00,67,00,65,00,73,00,2e,00,64,00,6c,00,6c,00,00,00 This entry corresponds to the path C:\windows\Microsoft.NET\Framework64\v2.0.50727\eventlogmessages.dll That is moreover, the only entry in "application" key related to OpsMgr....... Anyway, an entry exists also for OpsMgr config Service in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Operations Manager\OpsMgr Config Service with 2 subkeys: "EventMessageFile"="C:\\Program Files\\System Center Operations Manager 2007\\MOMMsgs.dll" "EventSourceFlags"=dword:00000000 Do you know why we have an entry in the key Eventlog\Application pointing on eventlogmessage.dll ? Anyway, I will test the suppression of the key "OpsMgr Config Service" in Application Key and give a further update. Thanks a lot. Patrick DEGOBERT

Hi again. after having deleted the "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\OpsMgr Config Service", the service system Center Management Configuration stays up. Thanks a lot. Regards. Patrick.